Fix: Added handling of PdfInteger for outlines #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ger instead of PdfReference. Added handling for that.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had a case where I merged multiple pdf files to one and added multilevel bookmarking at the same time. For some unknown(for me) reason with multilevel bookmarks there is sometimes PdfInteger instead of PdfReference and its causing:
System.InvalidCastException: 'Unable to cast object of type 'PdfSharp.Pdf.PdfInteger' to type 'PdfSharp.Pdf.Advanced.PdfReference'.'At PdfOutline.SplitDestinationPageI figured out the integer at least in my case was the actual page index so I added handling for that. In my case it did fix the problem.